Security News
GitHub Removes Malicious Pull Requests Targeting Open Source Repositories
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
workbox-cacheable-response
Advanced tools
This library takes a Response object and determines whether it's cacheable based on a specific configuration.
The workbox-cacheable-response npm package is part of the Workbox suite of libraries, which are designed to make it easier to build high-performance web applications with offline capabilities. This particular package provides tools to determine whether responses are cacheable based on certain criteria, such as status codes or headers. It's useful for service workers where you want to ensure that only certain responses are cached.
Caching responses based on status codes
This feature allows you to cache responses based on their HTTP status codes. In the code sample, only responses with status codes of 0 (opaque responses) or 200 (OK) are cached. This is particularly useful for caching successful responses or handling CORS requests in service workers.
workbox.routing.registerRoute(
({request}) => request.destination === 'image',
new workbox.strategies.CacheFirst({
cacheName: 'images',
plugins: [
new workbox.cacheableResponse.CacheableResponsePlugin({
statuses: [0, 200]
})
]
})
);
Caching responses based on headers
This feature enables caching of responses based on specific header values. In the example, only responses with a header 'X-Is-Cacheable' set to 'true' are considered cacheable. This allows for more granular control over what gets cached, based on server response headers.
workbox.routing.registerRoute(
({request}) => request.destination === 'document',
new workbox.strategies.NetworkFirst({
cacheName: 'documents',
plugins: [
new workbox.cacheableResponse.CacheableResponsePlugin({
headers: {
'X-Is-Cacheable': 'true'
}
})
]
})
);
sw-toolbox is a predecessor to Workbox, offering similar functionalities for caching strategies in service workers. While it provides tools for dynamic caching and runtime caching, it has been deprecated in favor of Workbox, which offers a more modular and flexible approach to building service workers.
sw-precache is another tool that was commonly used before Workbox for generating service worker files that precache resources. It focuses on static asset caching. Compared to workbox-cacheable-response, sw-precache is less flexible in terms of defining cacheable responses based on runtime conditions like status codes or headers.
This module's documentation can be found at https://developers.google.com/web/tools/workbox/modules/workbox-cacheable-response
FAQs
This library takes a Response object and determines whether it's cacheable based on a specific configuration.
The npm package workbox-cacheable-response receives a total of 2,380,436 weekly downloads. As such, workbox-cacheable-response popularity was classified as popular.
We found that workbox-cacheable-response demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 7 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
Security News
Node.js will be enforcing stricter semver-major PR policies a month before major releases to enhance stability and ensure reliable release candidates.